ci(governance): refresh stale hyperpolymath/standards reusable pins#96
Merged
Conversation
The governance / Hypatia / Scorecard reusables were pinned at 5a93d9d (stale), which failed two estate-governance checks on every PR off main: - "governance / Check Workflow Staleness" (pins behind current standards SHA) - "scan / Hypatia Neurosymbolic Analysis" (the old Hypatia reusable referenced actions/cache@d4373f2, a SHA that no longer resolves) Bump governance-reusable, hypatia-scan-reusable and scorecard-reusable from 5a93d9d -> d72fe5a (the SHA the staleness check compares against; it carries the cache/baseline-delay fix and keeps Scorecard out of Code Scanning). The legacy scorecard-enforcer.yml flagged by the same check was already removed on main. The secret-scanner and mirror reusables are pinned at different SHAs, were not flagged, and are left unchanged. Note: hyperpolymath/standards is not in this session's scope, so the target SHA is taken from the staleness check's own output rather than verified against the standards repo directly. This PR's own staleness check is the verification. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MWPX7iyvHf5AuwBAn1sJPy
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Two estate‑governance checks fail on every PR off current
main(they surfaced on #95 but are unrelated to that change):governance / Check Workflow Staleness— the repo pins thehyperpolymath/standardsgovernance, Hypatia, and Scorecard reusables at5a93d9d…, which is behind the current standards SHA (d72fe5a…).scan / Hypatia Neurosymbolic Analysis— fails at setup because the old Hypatia reusable (at5a93d9d…) referencesactions/cache@d4373f2…, a SHA that no longer resolves.Same root cause: stale reusable pins.
What
Bump the three flagged reusables
5a93d9d… → d72fe5a…:governance.ymlgovernance-reusable.ymlhypatia-scan.ymlhypatia-scan-reusable.ymlscorecard.ymlscorecard-reusable.ymld72fe5a…is the SHA the staleness check compares against; it carries the cache/baseline‑delay fix and keeps Scorecard out of Code Scanning. The legacyscorecard-enforcer.ymlthe same check wanted removed is already gone onmain.secret-scannerandmirrorare pinned at different SHAs, were not flagged, and are left unchanged.Verification & caveat
hyperpolymath/standardsisn't in this session's scope, so I took the target SHA from the staleness check's own log output rather than verifying it against the standards repo. This PR's owngovernance / staleness+ Hypatia checks are the verification — if standards has advanced pastd72fe5a…since, they'll name a newer SHA and I'll re‑bump.🤖 Generated with Claude Code
https://claude.ai/code/session_01MWPX7iyvHf5AuwBAn1sJPy
Generated by Claude Code